🦙 MegaLinter status: ⚠️ WARNING

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

How is it going? What is blocking it?

@bdovaz memory crash within the docker image... really hard to debug :/
but you can try with temp docker image generated by CI job

:/

🦙 MegaLinter status: ⚠️ WARNING

See detailed report in MegaLinter reports

You could have same capabilities but better runtime performances if you request a new MegaLinter flavor.

• Click here to request the new flavor

MegaLinter is graciously provided by

This pull request has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this pull request should stay open, please remove the O: stale 🤖 label or comment on the pull request.

This pull request has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this pull request should stay open, please remove the O: stale 🤖 label or comment on the pull request.

@nvuillam can you make a rebase? To at least check from time to time if this problem has been solved.

I would do it myself but I have doubts with utils.py and I prefer you to solve it.

@bdovaz done :)

@nvuillam Is it just me or seeing the result of the jobs, the random error that occurred no longer exists?

@nvuillam Is it just me or seeing the result of the jobs, the random error that occurred no longer exists?

ping @nvuillam

The error was not random... it was always and hard to diagnose its source ^^

Not crashing indeed !
But did i rebuild?

/build

Command run output
Build command workflow started.
Installing dependencies
Running script ./build.sh
Build command workflow completed without updating files.

@bdovaz I have a good feeling about this one... :D :D

@bdovaz @echoix @Kurt-von-Laven

Now I'm kind a afraid to release a new version... this PR is potentially very impacting, if you have some time please use beta versions in your repos to make sure that it still works well with relative files :) ( I'll obviously do the same on my side ^^ )

You could release a RC in the weekend and look at the number of pulls the following week to make sure that there was enough pulls.

Thanks for the heads up, @nvuillam. I tried the documentation, dotnet, javascript, and python flavors of the beta version on all of our repositories and encountered three issues. I am listing them all here for now since the second and third seem like they could potentially be related, but I am happy to file issues about these when I have more time tomorrow. The third issue is a preexisting issue that was made more visible by #2455, because previously ESLint silently didn't run at all locally.

1. CSharpier is broken; I am curious whether anyone else encounters this issue:

   ❌ Linted [CSHARP] files with [csharpier]: Found 1 error(s) - (1.18s)
   --Error detail:
   Run "dotnet tool restore" to make the "dotnet-csharpier" command available.
   
   Unable to get number of errors with regex_number and Issues found: ([0-9]+) in .* files
   

2. CSpell is broken when importing dictionaries that aren't bundled:

   ❌ Linted [SPELL] files with [cspell]: Found 1 error(s) - (18.84s)
   --Error detail:
   Configuration Error: Failed to read config file: "/tmp/lint/@cspell/dict-medicalterms/cspell-ext.json"
   CSpell: Files checked: 0, Issues found: 0 in 0 files
   
   ❌ Error(s) have been found during linting
   

   Our cspell.config.yaml contains:

   import:
     - "@cspell/dict-medicalterms/cspell-ext.json"

   Our .mega-linter.yaml contains:

   SPELL_CSPELL_CONFIG_FILE: LINTER_DEFAULT
   SPELL_CSPELL_PRE_COMMANDS:
     - command: npm install @cspell/dict-medicalterms@3.0.0

3. In our Yarn TypeScript projects, there is one error per file of the following form:

   ❌ Linted [TYPESCRIPT] files with [eslint]
   --Error detail:
   
   /tmp/lint/some_file.ts
     0:0  error  Parsing error: File '@tsconfig/node18-strictest-esm/tsconfig.json' not found
   

   Our tsconfig.json contains:

   {
     "extends": "@tsconfig/node18-strictest-esm/tsconfig.json"
   }

   Our package.json contains:

   {
     "devDependencies": {
       "@tsconfig/node18-strictest-esm": "1.0.1"
     }
   }

   Our .eslintrc.yaml is:

   root: true
   extends:
     - eslint:recommended
     - plugin:@typescript-eslint/recommended
     - prettier
   parser: "@typescript-eslint/parser"
   parserOptions:
     project:
       - tsconfig.json
   plugins:
     - "@typescript-eslint"
   env:
     node: true

If it makes you feel any better, passing relative file paths fixed the error originally reported in #1572, getting ESLint running in list_of_files mode for npm projects and unblocking running ESLint in list_of_files mode for Yarn PnP projects.

@Kurt-von-Laven I'm trying to fix that in #2601 ... the idea is the following:

• check if PRE_COMMANDS contain "npm" or "yarn"
• if yes:
  • copy /node_deps into workspace+"node_modules"
  • Add workspace+"node_modules" in PATH
  • run the PRE_COMMANDS

Do you think it could work ? ^^